chore(main): release v0.2.1 - #34

• Merging this pull request tags v0.2.1, creates the release and moves the label to release: tagged. With major-tag enabled, the moving major tag follows a stable release.
• Release notes: add a fenced block with the info string release-me-notes anywhere in this body. It is rendered above the changelog in the GitHub release, never in the changelog file, and survives updates.
• Force the next version: add a fenced block with the info string release-me-version containing X.Y.Z anywhere in this body, or comment the configured mention followed by release-as X.Y.Z. It wins outright over the computed bump, pre-release label included, until the pull request merges or the block is removed; one that does not parse, or is not greater than the last released version, is ignored instead.
• Pre-release: add the label release: alpha, release: beta or release: rc. The next run turns the version into X.Y.Z-<type>.N. Remove the label to go back to the stable version.
• Hide or rewrite a change: a fenced block release-me in the changed pull request's body, one conventional line per entry, an empty block hides it.
• Every push to the default branch updates this pull request. Edits to the body outside the notes block are overwritten.

v0.2.1 (2026-11-13)

Bug Fixes

• renovate-config: pin an explicit Node.js version (#33)